home *** CD-ROM | disk | FTP | other *** search
- Path: redstone.interpath.net!mercury!softbase
- From: softbase@mercury.interpath.net (Scott McMahan - Softbase Systems)
- Newsgroups: comp.lang.c++
- Subject: Re: Visual c++ 1.00
- Date: 25 Feb 1996 19:48:37 GMT
- Organization: Interpath -- Providing Internet access to North Carolina
- Message-ID: <4gqeel$jfo@redstone.interpath.net>
- References: <824988310snz@seacloud.demon.co.uk>
- NNTP-Posting-Host: mercury.interpath.com
- X-Newsreader: TIN [version 1.2 PL2]
-
- Ben Ashley (Ben@seacloud.demon.co.uk) wrote:
-
- : Basically what I am asking, is how to access the properties of controls you
- : have defined.
-
- Oops, you've been caught using the wrong paradigm at the wrong time.
-
- Visual Basic and Delphi are based on OBJECTS: things on the screen have
- properties and methods. You change these to change the screen.
-
- MFC and OWL are based on MESSAGES: you have an application class which
- has a message handler for each WM_* message you can receive. This is
- like 0.5 steps above the C SDK way of doing things. The big difference
- is replacing one central switch with a lot of little functions.
-
- And neither the twain shall meet, unless Borland really does add Delphi
- stuff to BC++.
-
- What you need to do is step back and read Programming Windows by
- Charles Petzold and see how they do it the old fashioned way. Then
- approach MFC from that standpoint. VB/Delphi know-how is practically
- useless.
-
- Scott
-
-